Repository navigation
[PWGDQ] Adding a configurable to mute histograms from ambiguous tracks - #18733
JonathanWitte wants to merge 1 commit into
Conversation
|
Hi @JonathanWitte, I think that the same event pairing task has quite a lot of configurables already, so I am a bit skeptical in adding so fine tuning for histograms output. Moreover, the ambiguous histograms are needed, since you have to take into account the double counting in your analysis. So, not sure why you would want to switch them off. In the worse case, I would go for just one single configurable. Since typically you do not run simultaneously the barrel and muon analyses, a single configurable should be enough. But I would consider not adding them, since this is complicating even more the logic in the init function. So, unless you have a very good reason, I would not merge this PR at all. Note that if you want to avoid having too many histograms, you can always use the json options, and add your main pairing histograms just in the directories you want. |
To fix the problem of default ambiguity histograms filling up memory, I included a variable to mute this histograms.
For the muon part, the variable was already in place in the tableReader, so I recycled the functionality in dq-efficiency and added a similar one for the barrel